Establishing secure, mutually authenticated communication credentials

ABSTRACT

Establishing secure, mutually authenticated communication between a trusted network and a perimeter network. Servers on the perimeter network may be securely and automatically configured to communicate with the trusted network. Servers not functioning properly may be stopped from communicating with the other servers. Credential information relating to a perimeter server may be automatically, and regularly, updated without intervention.

Large networks are often organized to enhance security from outside attack. A common architecture for such a network includes a perimeter network, or DMZ (i.e., demilitarized zone), that surrounds a trusted network and acts as a buffer between the trusted network and the broader (e.g., global) computing network. These perimeter networks are utilized as a first line of defense against attack from entities residing in the broader network. As a first line of defense, devices and data stored upon the perimeter network are assumed to be at greater risk of attack. Thus, network designers carefully consider what data is placed on devices residing in such perimeter networks. For example, a common task for servers placed on a perimeter network is the routing of e-mails to users within the trusted network. To perform such routing functions, these servers need some information related to the users on the trusted network. Such data is readily available on the trusted network, such as through a distributed directory service containing configuration information (e.g., Microsoft Windows® Active Directory for Windows Server 2003). But because of the increased vulnerability of the perimeter network servers to attack, it is advantageous to limit the quantity and type of data replicated from the distributed directory service on the trusted network and placed upon the perimeter network servers. For the e-mail routing example, e-mail addresses may be stored on servers in the perimeter network, while other information about users is stored on the distributed directory service of the trusted network.

In addition to limiting the amount and type of information placed upon the perimeter network servers, the communication link between the perimeter network and the trusted network must be secure. In particular, establishing a secure communication link means establishing a mutually authenticated, authorized, and encrypted communication channel (e.g., an LDAP (Lightweight Directory Access Protocol) communication channel, among others) between the trusted network and the perimeter network. For this purpose, particular credentials can be created, whose password remains secure, to provide for secure communication between the trusted network and the perimeter network. Moreover, servers running in a conventional perimeter network must be individually, manually configured. A method for commonly configuring servers in the perimeter network once via the distributed directory service and replicating the configuration securely to the perimeter network would be beneficial.

Updating such credentials periodically can also be cumbersome conventionally. New passwords must be generated and utilized before current passwords expire. The coordination of such credential updates can be time-consuming, for example, if performed manually. A method for automatically updating such credentials before their expiration would be beneficial.

In addition to providing communication between the trusted network and the perimeter network, some situations require the removal of a particular server from communicating with other servers, such as to protect the other servers from a problem with the removed server, such as removal of a server that has potentially been compromised. A system allowing such removal of a suspect server in a rapid fashion, without requiring physical and/or manual access to the server in question, so that other servers are protected from the potentially compromised server, would be beneficial. The more quickly such a server can be removed from communication with other servers, the more likely the ill effects attributable to the server can be avoided.

SUMMARY

The following simplified summary provides a basic overview of some aspects of the present technology. This summary is not an extensive overview. It is not intended to identify key or critical elements or to delineate the scope of this technology. This Summary is not intended to be used as an aid in determining the scope of the claimed subject matter. Its purpose is to present some simplified concepts related to the technology before the more detailed description presented below.

Accordingly, aspects of embodiments of the invention provide for establishing secure, mutually authenticated communication between a trusted network and a perimeter network. By establishing secure communication, aspects of embodiments of the invention permit automatic configuration of servers on the perimeter network. Moreover, by providing a means for limiting the communication with a particular server, aspects of embodiments of the invention can isolate servers not functioning properly, such as those having compromised security. In addition, by providing a method for automatically updating credential information, aspects of embodiments of the invention can automatically sustain communication while updating credential information changes without manual intervention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of a system of one embodiment of the invention;

FIG. 2 is a flow diagram of a method of one embodiment of the invention;

FIG. 3 is a flow diagram of another method of another embodiment of the invention; and

FIG. 4 is a flow diagram of still another method of still another embodiment of the invention.

Corresponding reference characters indicate corresponding parts throughout the drawings.

DETAILED DESCRIPTION

Referring now to FIG. 1, a system, generally indicated 21, for establishing secure, mutually authenticated communication between a trusted network 23 and a perimeter network 25 outside the trusted network. In particular, as discussed in greater detail below with respect to exemplary methods of the present invention, aspects of the embodied invention transfer a public key and a bootstrap password from the perimeter network 25 to the trusted network 23 for authenticating communication between the two. The trusted network 23 exists, for example, behind an interior firewall 29 separating the perimeter network 25 and the trusted network 23. In one exemplary embodiment, the trusted network 23 is a corporate network, and the perimeter network 25 is a DMZ protecting the corporate network.

The system 21 comprises one or more master servers 31, or domain controllers, residing in the trusted network 23. In the example of FIG. 1, three master servers, a first master server 31A, a second master server 31B, and a third master server 31C, are each adapted for administering a distributed directory service 33 containing configuration information related to the trusted network 23. As used herein, for example, the configuration information can include system configuration data, recipient data, and/or routing data, among others. Each of the master servers 31A, 31B, and 31C is adapted for administering a first copy of the distributed directory service 33A, a second copy of the distributed directory service 33B, and a third copy of the distributed directory service 33C, respectively. Each distributed directory service 33A, 33B, and 33C contains the same configuration information related to the trusted network 23. In one example, the distributed directory service 33 is Microsoft Windows® Active Directory for Windows Server 2003, although the master servers may administer other alternative distributed directory services without departing from the scope of embodiments of the invention. When administering such a distributed directory service 33 on a trusted network 23, an administrator accessing any of the master servers 31 may add to, delete from, or modify the configuration information stored on the accessed master server. The distributed directory service 33 is responsible for updating the configuration information on the other master servers 31 according to the additions, deletions, or modifications resulting from the actions of the administrator.

The system 21 also comprises one or more edge servers 37 residing in the perimeter network 25 outside the trusted network 23. In the example of FIG. 1, three edge servers, a first edge server 37A, a second edge server 37B, and a third edge server 37C, are each adapted for administering a stand-alone directory service 39. Each of the edge servers 31A, 31B, and 31B is adapted for administering a first copy of the stand-alone directory service 39A, a second copy of the stand-alone directory service 39B, and a third copy of the stand-alone directory service 39C, respectively. In one example, the stand-alone directory service 93 is Microsoft Active Directory Application Mode for Windows Server 2003, although the edge servers may administer other alternative stand-alone directory services without departing from the scope of embodiments of the invention. The one or more edge servers 37 are adapted for communicating with a network 43 (e.g., the Internet) outside the perimeter network 25. In the example shown, an exterior firewall 45 separates the one or more edge servers 37 residing in the perimeter network 25 from the network 43 outside the perimeter network. Any of a variety of alternative firewall applications and other additional or alternative security measures may be utilized without departing from the scope of the embodiments of the invention.

The system 21 further comprises one or more edge-connected bridgehead servers 51 residing in the trusted network 23 and adapted for communicating with the one or more master servers 31. The edge-connected bridgehead servers 51 communicate with the master servers 31 to obtain configuration information stored in the distributed directory service 33. In the example shown, the edge-connected bridgehead servers 51 utilize trusted network 23 secured LDAP 53 to communicate with the master servers 31, although other alternative protocols may be utilized without departing from the scope of embodiments of the invention. In the example shown, a first edge-connected bridgehead server 51A communicates with the first master server 31A, while the second edge-connected bridgehead server 51B communicates with the second master server 31B and the third master server 31C. As would be readily understood by one skilled in the art, an edge-connected bridgehead server 51 can communicate with one or more master servers 31 separately or in combination without departing from the scope of embodiments of the invention. Moreover, one skilled in the art will also recognize that one or more master servers 31 in the trusted network 23 may be assigned to function as bridgehead servers 51.

The edge-connected bridgehead servers 51 are adapted for replicating the configuration information from the distributed directory service 33 administered by the one or more master servers 31 within the trusted network 23 to the stand-alone directory service 39 administered by the one or more edge servers 37 within the perimeter network 25. The configuration information is replicated from the edge-connected bridgehead servers 51 to the edge servers 37 using internal firewall 29 secured LDAP 57, although other protocols may be utilized without departing from the scope of embodiments of the invention.

In one example, the edge-connected bridgehead servers 51 execute a replication application 55 for performing such replication of configuration information to the stand-alone directory service 39 administered by the one or more edge servers 37. The replication application 55 can perform several functions, including (i) scheduling the interaction between the distributed directory service 33 on the master server 31 and the stand-alone directory service 39 on the edge server, (ii) replication of configuration information to the perimeter network 25 via LDAP, (iii) determining the topology of the components of the system 21, (iv) locking particular edge servers 37 from use, among others. Other alternative functions may also be performed without departing from the scope of embodiments of the invention. Moreover, in the example shown, the first edge-connected bridgehead server 51A communicates with both the first edge server 37A and the second edge server 37B, while the second edge-connected bridgehead server 51B communicates with the third edge server 37C. As would be readily understood by one skilled in the art, an edge-connected bridgehead server 51 can communicate with one or more edge servers 37 without departing from the scope of embodiments of the invention. Other alternative configurations are also contemplated.

The system 21 may also comprise other components. For example, the system 21 depicted in FIG. 1 includes an exemplary client mailbox 61 for use by an information worker (IW) communicating with one of the master servers 31 via trusted network 23 secured LDAP 53. In addition, the system 21 includes a bridgehead server 63 communicating with a master server 31, but not functioning as an edge-connected bridgehead server. Other alternative components may be utilized without departing from the scope of embodiments of the invention.

An exemplary flow diagram, generally indicated at 81 in FIG. 2, illustrates aspects of a method for establishing secure, mutually authenticated communication between trusted servers 51 (e.g., an edge-connected bridgehead server) of a trusted network 23 and an edge server 37 of a perimeter network 25 outside the trusted network. Beginning at 83, aspects of the embodied invention create a self-signed certificate for secure SSL (secure sockets layer) connection on the edge server 37 in the perimeter network 25. Such a secure SSL connection may be utilized throughout the present method 81. As would be readily understood by one skilled in the art, the self-signed certificate may be of another security and privacy protocol without departing from the scope of the aspects of the embodied invention.

Proceeding to 85, aspects of the embodied invention create a public key, a private key, and a password associated with the edge server 37 in the perimeter network 25 with the certificate. In one example, the public key, the private key, and the password are created as part of the certificate. Moreover, in another example, the method provides different security levels for different types of data that require independent protection. For example, one or more other public/private key combinations not associated with the certificate, or any certificate, may be utilized to provide different security levels for other data.

Aspects of the embodied invention further store, at 87, a private key associated with the public key on the edge server 37 in the perimeter network 25. As would be readily understood by one skilled in the art, the edge server 37 may provide its public key to other entities (e.g., servers), such that those entities can use its public key to encrypt data that only the edge server 37 can decrypt with its private key.

At 93, aspects of the embodied invention transfer securely the self-signed certificate with the public key and the password (e.g., a bootstrap password) from the edge server 37 of the perimeter network 25 to the distributed directory service 33 of the trusted network 23. In one exemplary embodiment, the transferring securely comprises transferring manually, also at 93, the self-signed certificate with the public key and the password to the trusted network 23. As used herein, the term “manually” means human-directed, as compared with automatically directed, such as by a computer application. An example of such a manual transfer, may include hand-carrying a memory storage device, such as a USB drive or floppy disc from a machine operating in the perimeter network 25 to a machine operating in the trusted network 23. Further aspects of the embodied invention maintain, also at 93, the self-signed certificate with the public key and the password in a secure state during the manual transfer. For example, the public key and password may be pin-protected on the memory storage device for further protection in the event of loss of physical control of the memory storage device. In another exemplary embodiment, the transferring securely 93 further comprises transferring securely a location identifier associated with the edge server. In still another exemplary embodiment, a secure, direct electronic transfer mechanism may be utilized for securely transferring the self-signed certificate with the public key and the password.

Within the trusted network 23, aspects of the embodied invention further create, at 95, an edge configuration object associated with the edge server 37 on the distributed directory service 33 administered within the trusted network. In one example, the edge configuration object is created immediately after the secure transfer 93 of the public key and the password, so that this data is available to create the correct object in the distributed directory service 33. The edge configuration object resides on each of the master servers 31 administering the distributed directory service 33. This edge configuration object can retain configuration information related to the edge server 37. Although the present explanation of exemplary method 81 utilizes a single edge server 37, additional edge servers may also be included. Each such additional edge server 37 will include a corresponding edge configuration object on each master server 31 administering the distributed directory service 33.

The operations continue by placing, at 97, the public key and the password on the corresponding edge configuration object. For example, the edge configuration object may reside on one of the trusted servers 31 (e.g., a master server) administering the distributed directory service 33 within the trusted network 23. In a more specific example, such placing 97 may be accomplished by a system administrator by storing the public key and the password on the edge configuration object of the distributed directory service 33. Once the public key and password are within the trusted network, the distributed directory service 33 updates, at 101, the public key and password associated with the edge server to two or more of the trusted servers 51 adapted for communicating with the perimeter network 25 (e.g., edge-connected bridgehead servers), thereby identifying the edge server 37 to each of the trusted servers as a registered edge server. Once the public key and password are placed 97 upon the corresponding edge configuration object, the public key and password information initially stored during the secure transfer 93, such as on the memory storage device, should be destroyed to minimize the risk of an unsecured release of such information.

Now that each of the trusted servers 51 adapted for communicating with the perimeter network 25 has received the public key and password of the edge server 37, each such trusted server further encrypts, at 103, its own particular password with the public key created by the edge server. This encryption ensures that only the edge server 37 holding the private key associated with the public key can decrypt the particular password associated with and generated by the trusted server 51. In one example, authenticity may be further secured by each of the trusted servers 51 digitally signing the encrypted credential information, thereby authenticating it. Proceeding to 105, aspects of the embodied invention send, by each trusted server 51, a password associated with each particular trusted server encrypted with a private key associated with the particular trusted server to the edge server 37 for authenticating the edge server with respect to each trusted server. The public key corresponding to the private key of each trusted server 51 is already available at the edge servers 37 for decrypting the encrypted passwords of each of the trusted servers. In one exemplary embodiment, the sending comprises sending, also at 105, through the secure SSL established by the self-signed certificate. As would be readily understood by one skilled in the art, other protocols, such as an HTTP/XML (hypertext transfer protocol/extensible markup language) based protocol, may be utilized without departing from the scope of the present invention. In another exemplary embodiment, the sending 105 the encrypted password comprises sending the encrypted password to a stand-alone directory service administered by the edge server 37 being authenticated.

Another exemplary flow diagram, generally indicated at 111 in FIG. 3, illustrates aspects of a method for automatically updating credential information between a trusted server 51 residing on a trusted network 23 and an edge server 37 residing on a perimeter network 25. Beginning at 113, aspects of the embodied invention read, by the trusted server 51, the current credential information of the edge server 37 residing on the perimeter network 25. Proceeding to 115, aspects of the embodied invention determine the expiration status of the current credential information on the edge server. For example, the credential information may include an expiration time indicating the time at which the credential information expires.

Generally speaking aspects of the embodied invention further create, at 121, replacement credential information when a replacement criterion is met. In one embodiment, the creating 121 replacement credential information occurs when at least one of the following replacement criteria is met: (i) the current credential information is near expiration and (ii) a time limit has passed. In the exemplary flow diagram of FIG. 3, decision element 125 determines if the current credentials are near expiration, and decision element 127 determines if a time limit has passed. An affirmative answer to either of these decision elements 125, 127 invokes creation 121 of replacement credential information. Alternately, a negative answer to both of these decision elements 125, 127 invokes a return to the reading 113 operation discussed above.

For example, an appropriate time limit may be utilized to ensure that the password is updated properly. Where the password must be updated every 60 days, the time limit for creating a new password may be set to 55 days. In this manner, a replacement password is created at day 55 in the life of a 60 day password, so that the first password is never allowed to expire. In an alternate example, the expiration date of the current credential information may be utilized as a trigger. For example, when the expiration date of the current credential information is within the next seven days, the method creates a replacement password. In this manner, the replacement credential information is created and utilized before the current credential information is allowed to expire. Other triggers for replacement of the credential information may be utilized without departing from the scope of the embodied invention. In another example, two sets of credential information are initially created, and only a first set is immediately utilized, while the other is maintained for later use. Once the first set of credential information expires and/or fails to function, the second set of maintained credential information is readily available as replacement credential information. The first set of expired credential information is then updated for use again and maintained for when the second set expires and/or fails to function. This process is repeated, whereby the replacement credential information is created immediately after expiration and/or failure of the previous credential information, such that an extra set of credential information is available.

In one example, the creating 121 replacement credential information comprises encrypting, at 123, the replacement credential information for the edge server 37 and placing, also at 23, the replacement credential information on an edge configuration object associated with the edge server. In one example, the distributed directory service 33 provides the edge configuration object. In another exemplary embodiment, the replacement credential information may be otherwise delivered to the edge server 37 securely.

In another further example the credential information comprises a password, whereby the reading 113 discussed above comprises reading a password of the edge server 37. Similarly, the encrypting 123 discussed above comprises encrypting a replacement password. In still further password examples, the encrypting 123 a replacement password comprises encrypting a replacement password including non-ASCII characters. Including non-ASCII characters in a password makes the password more unique, because more characters are available. Alternatively, the encrypting 123 a replacement password can further comprise encrypting a replacement password created automatically by a random number generator. This ensures that the password is unique and does not include any unintentional pattern, as may be the case with human-defined passwords. In still another example, the encrypting 123 a replacement password can comprise encrypting a replacement password including a maximum number of allowable characters. For example, the maximum number of allowable characters may be limited by the operating system executed by servers on the trusted and perimeter networks 23, 25. Allowing encryption of a password as long as permitted by the operating system, the password's uniqueness is further enhanced. Other password enhancements may also be utilized without departing from the scope of embodiments of the embodied invention.

At 131, aspects of the embodied invention propagate the replacement credential information from the distributed directory service 33 to the edge server 37 by any trusted server 51. In other words, any of the edge-connected bridgehead servers 51 may propagate the replacement credential information to the edge server 37. In one example, the propagating 131 the replacement credential information occurs with any trusted server 51 adapted for communication with the perimeter network 25. In one example, authenticity may be further secured if each of the trusted servers 51 digitally signs the credential information, thereby authenticating the credential information. Once propagated, aspects of the embodied invention may further comprise verifying 135, at the edge server 37, that the appropriate trusted server 51 has signed the credentials. This verification 135 ensures that one trusted server 51 has not signed credentials for another trusted server. Where the wrong trusted server 51 has signed the credentials, the replacement credentials are rejected, at 137, and the method 111 returns to repeat the reading operation 113.

Where the correct trusted server 51 has signed the credentials, the method continues. At this point, both the current credentials and the replacement credentials exist on the trusted server 51, and the trusted server continues to the utilized the current credentials to communication with the edge server 37. At some point, however, the current credentials will fail to work. Proceeding to 141, a decision element determines if the current credentials fail to work. When an attempt to utilize the current credential information fails, aspects of the embodied invention further utilize, at 143, by the trusted server 51, the replacement credential information. Aspects of the embodied invention further delete, at 145, the current credential information when the attempt to utilize the replacement credential information is successful. The method 111 then returns to the reading 113 operation discussed above, to restart the process with the replacement credential information. Alternately, when an attempt to utilize the current credential information is successful, aspects of the embodied invention further hold, at 147, the replacement credentials and continue using the current credentials until they fail, as described above.

By this method 111, the trusted server 51 can continually review and revise the password associated with the edge server 37. By this method 111, the password may be continually changed, thereby enhancing security, without the added work of manually changing the password periodically.

Still another exemplary flow diagram, generally indicated at 151 in FIG. 4, illustrates aspects of a method for disenfranchising a server residing on a trusted network 23 or a perimeter network 25 from communication with other servers on the trusted network or the perimeter network. As above, the trusted network 23 administers a distributed directory service 33 comprising credential information corresponding to each of the servers on the trusted network 23 and the perimeter network 25. As used herein, the term “disenfranchisement” refers to prohibiting a server from communicating with other servers by removing its ability to authenticate communications with other servers.

Beginning at 155, aspects of the embodied invention receive instructions from an administrator from within the trusted network 23 instructing that one of the servers requires disenfranchisement from communicating with the other servers. The disenfranchisement of a particular server may occur for a variety of reasons. In one example, the receiving instructions 155 comprises receiving an indication that the server requiring disenfranchisement poses a security risk. In this example, a ready means for disenfranchising a server that poses a security risk, without having to physically act upon the server, is useful. For example, a server may be disenfranchised remotely. Also, where the server is a security risk because of an application has taken control over the server, the server itself may be difficult to control. But the present method provides for an external means for simply stopping other, readily controllable servers from communicating with the server at risk. In this manner, the server is cut off without requiring any control over the actual server itself. In another example, the server may need to be removed from the system momentarily for service, or for some other reason unrelated to security, without departing from the scope of embodiments of the present invention.

Proceeding to 159, aspects of the embodied invention delete credential information associated with the server requiring disenfranchisement within the distributed directory service 33. This eliminates the ability of any server on the trusted network 23 or the perimeter network 25 to establish communication with the server with deleted credential information. As noted above, this deletion 159 of the credential information essentially makes the disenfranchised server invisible to the other servers, whereby no server can communicate with the disenfranchised server. In another embodiment, the deleting 159 credential information associated with a server comprises deleting a configuration object associated with the server on the distributed directory service 33 administered by the trusted network 23.

Continuing with 161, the method further monitors the status of the servers for to determine if another server requires disenfranchisement. Monitoring 161 continues if no further servers require disenfranchisement. The method 151 returns to the receiving 155 if another server requires disenfranchisement.

Those skilled in the art will note that the order of execution or performance of the methods illustrated and described herein is not essential, unless otherwise specified. That is, it is contemplated by the inventors that elements of the methods may be performed in any order, unless otherwise specified, and that the methods may include more or less elements than those disclosed herein.

When introducing elements of the present invention or the embodiment(s) thereof, the articles “a,” “an,” “the,” and “said” are intended to mean that there are one or more of the elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements.

As various changes could be made in the above products and methods without departing from the scope of the invention, it is intended that all matter contained in the above description and shown in the accompanying drawings shall be interpreted as illustrative and not in a limiting sense. 

1. A method for establishing secure, mutually authenticated communication between trusted servers of a trusted network and an edge server of a perimeter network outside the trusted network, said method comprising: creating a public key and a password associated with the edge server in the perimeter network; transferring securely the public key and the password to the trusted network; creating an edge configuration object associated with the edge server on a distributed directory service administered within the trusted network; placing the public key and the password on the corresponding created edge configuration object of the distributed directory service within the trusted network; updating, by the distributed directory service, the public key and password associated with the edge server to two or more of the trusted servers on the trusted network adapted for communicating with the perimeter network, thereby identifying the edge server to each of the trusted servers adapted for communicating with the perimeter network as a registered edge server; encrypting, by each trusted server adapted for communicating with the perimeter network, a password associated with the particular trusted server with the public key created by the edge server; and sending, by each trusted server adapted for communicating with the perimeter network, a password associated with each particular trusted server encrypted with a private key associated with the particular trusted server to the edge server for authenticating the edge server with respect to each respective trusted server.
 2. A method as set forth in claim 1 further comprising storing a private key associated with the public key on the edge server in the perimeter network.
 3. A method as set forth in claim 1 further comprising creating a self-signed certificate for secure SSL (secure sockets layer) connection on an edge server, said public key and said password associated with said self-signed certificate, wherein said transferring securely comprises transferring manually the self-signed certificate with the public key and the password to the trusted network.
 4. A method as set forth in claim 3 further comprising maintaining the self-signed certificate with the public key and the password in a secure state during said transferring manually.
 5. A method as set forth in claim 3 wherein said sending comprises sending through the secure SSL established by the self-signed certificate.
 6. A method as set forth in claim 1 wherein said transferring securely further comprises transferring securely a location identifier associated with the edge server.
 7. A method as set forth in claim 1 wherein said sending an encrypted password comprises sending the encrypted password to a stand-alone directory service administered by the edge server being authenticated.
 8. A method for automatically updating credential information between a trusted server residing on a trusted network and an edge server residing on a perimeter network, said trusted network administering a distributed directory service, said method comprising: reading, by the trusted server, the current credential information of the edge server residing on the perimeter network; determining the expiration status of the current credential information on the edge server; propagating the replacement credential information from the distributed directory service to the edge server by any trusted server; and utilizing, by the trusted server, the replacement credential information when an attempt to utilize the current credential information fails.
 9. A method as set forth in claim 8 further comprising deleting the current credential information when an attempt to utilize the replacement credential information is successful.
 10. A method as set forth in claim 8 further comprising creating replacement credential information when a replacement criteria is met.
 11. A method as set forth in claim 10 wherein said creating replacement credential information comprises: encrypting the replacement credential information for the edge server; and placing the replacement credential information on an edge configuration object of the distributed directory service associated with the edge server.
 12. A method as set forth in claim 11 wherein said reading the current credential information comprises reading a password of the edge server; and wherein said encrypting the replacement credential information comprises encrypting a replacement password.
 13. A method as set forth in claim 12 wherein said encrypting a replacement password comprises encrypting a replacement password including non-ASCII characters.
 14. A method as set forth in claim 12 wherein said encrypting a replacement password comprises encrypting a replacement password created automatically by a random number generator.
 15. A method as set forth in claim 12 wherein said encrypting a replacement password comprises encrypting a replacement password including a maximum number of allowable characters.
 16. A method as set forth in claim 10 wherein said creating replacement credential information comprises digitally signing, by each trusted server, the credential information of the particular trusted server with a private key created by the trusted server, said method further comprising verifying, at the edge server, that each particular trusted server has digitally signed its respective credentials.
 17. A method as set forth in claim 8 wherein said propagating the replacement credential information occurs with any trusted server adapted for communication with the perimeter network.
 18. A method for disenfranchising a server residing on a trusted network or a perimeter network from communication with other servers on the trusted network or the perimeter network, said trusted network administering a distributed directory service comprising credential information corresponding to each of the servers on the trusted network and the perimeter network, said method comprising: receiving instructions from an administrator from within the trusted network instructing that one of the servers requires disenfranchisement from communicating with the other servers; and deleting credential information associated with the server requiring disenfranchisement within the distributed directory service, thereby eliminating the ability of any server on the trusted network or the perimeter network to establish communication with the server with deleted credential information.
 19. A method as set forth in claim 18 wherein said deleting credential information associated with a server comprises deleting a configuration object associated with the server on the distributed directory service administered by the trusted network.
 20. A method as set forth in claim 18 wherein said receiving instructions comprises receiving an indication that the server requiring disenfranchisement poses a security risk. 